Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore previous lightning setup #49

Open
wants to merge 7 commits into
base: develop
Choose a base branch
from
Open

Conversation

dborowiecki
Copy link
Contributor

Changes:

  • remove additional service for lightning db
  • fixed env values
  • changed .env to .env.lightning for lightning setup
  • exposed port 4000 for lightning
  • added lightning service to openIMIS network
  • changed service name from web to lightning

@gitguardian
Copy link

gitguardian bot commented Sep 25, 2023

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id Secret Commit Filename
8234759 Company Email Password 3335b46 .env.lightning.example View secret
5034616 Generic Database Assignment ad9c31a .env.example View secret
5034616 Generic Database Assignment 6a2e42c .env.example View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant